Methods for vehicular communication in accordance with co-existence between next generation vehicle-to-everything (ngv) devices and legacy devices

ABSTRACT

Embodiments of a Next Generation Vehicle-to-Everything (NGV) station (STA) and method of communication are generally described herein. The NGV STA may encode a physical layer convergence procedure (PLCP) protocol data unit (PPDU) for transmission in a dedicated short-range communication (DSRC) frequency band allocated for vehicular communication by NGV STAs and legacy STAs. In some cases, the NGV STA may encode the PPDU in accordance with an NGV enhanced physical (PHY) layer protocol, and includes usage of a mid-amble, space-time block coding (STBC), or low-density parity check (LDPC) coding. In other cases, the NGV STA may encode the PPDU in accordance with a legacy PHY layer protocol that is compatible with the legacy STAs, and excludes usage of the mid-amble, the STBC, and the LDCP coding.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.16/403,046, filed May 3, 2019, which claims priority under 35 U.S.C.119(e) to U.S. Provisional Patent Application Ser. No. 62/666,857, filedMay 4, 2018 [reference number AB0943-Z, 1884.758PRV], and to U.S.Provisional Patent Application Ser. No. 62/669,012, filed May 9, 2018[reference number AB0944-Z, 1884.759PRV], each of which is incorporatedherein by reference in its entirety.

TECHNICAL FIELD

Embodiments pertain to wireless networks and wireless communications.Some embodiments relate to wireless local area networks (WLANs) andWi-Fi networks including networks operating in accordance with the IEEE802.11 family of standards. Some embodiments relate to IEEE 802.11bd.Some embodiments relate to IEEE 802.11p. Some embodiments relate tomethods, computer readable media, and apparatus to enable co-existencebetween devices that support IEEE 802.11bd and legacy devices, includingbut not limited to devices that support 802.11p.

BACKGROUND

Efficient use of the resources of a wireless local-area network (WLAN)is important to provide bandwidth and acceptable response times to theusers of the WLAN. However, often there are many devices trying to sharethe same resources and some devices may be limited by the communicationprotocol they use or by their hardware bandwidth. Moreover, wirelessdevices may need to operate with both newer protocols and with legacydevice protocols.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a block diagram of a radio architecture in accordance withsome embodiments;

FIG. 2 illustrates a front-end module circuitry for use in the radioarchitecture of FIG. 1 in accordance with some embodiments;

FIG. 3 illustrates a radio IC circuitry for use in the radioarchitecture of FIG. 1 in accordance with some embodiments;

FIG. 4 illustrates a baseband processing circuitry for use in the radioarchitecture of FIG. 1 in accordance with some embodiments;

FIG. 5 illustrates a WLAN in accordance with some embodiments;

FIG. 6 illustrates a block diagram of an example machine upon which anyone or more of the techniques (e.g., methodologies) discussed herein mayperform;

FIG. 7 illustrates a block diagram of an example wireless device uponwhich any one or more of the techniques (e.g., methodologies oroperations) discussed herein may perform;

FIG. 8 illustrates the operation of a method in accordance with someembodiments;

FIG. 9 illustrates the operation of another method in accordance withsome embodiments;

FIG. 10 illustrates a dedicated short-range communication (DSRC)frequency allocation in accordance with some embodiments;

FIG. 11 illustrates a protocol stack in accordance with someembodiments;

FIG. 12 illustrates an example arrangement of multiple transmit chainsin accordance with some embodiments; and

FIG. 13 illustrates example elements and fields in accordance with someembodiments.

DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1 is a block diagram of a radio architecture 100 in accordance withsome embodiments. Radio architecture 100 may include radio front-endmodule (FEM) circuitry 104, radio IC circuitry 106 and basebandprocessing circuitry 108. Radio architecture 100 as shown includes bothWireless Local Area Network (WLAN) functionality and Bluetooth (BT)functionality although embodiments are not so limited. In thisdisclosure, “WLAN” and “Wi-Fi” are used interchangeably. Embodiments arenot limited to the radio architecture 100. In some embodiments, an802.11bd radio unit may be used for vehicular communication and an802.11 radio unit may be used for other communications, including butnot limited to cellular communication and Bluetooth communication.

FEM circuitry 104 may include a WLAN or Wi-Fi FEM circuitry 104A and aBluetooth (BT) FEM circuitry 104B. The WLAN FEM circuitry 104A mayinclude a receive signal path comprising circuitry configured to operateon WLAN RF signals received from one or more antennas 101, to amplifythe received signals and to provide the amplified versions of thereceived signals to the WLAN radio IC circuitry 106A for furtherprocessing. The BT FEM circuitry 104B may include a receive signal pathwhich may include circuitry configured to operate on BT RF signalsreceived from one or more antennas 101, to amplify the received signalsand to provide the amplified versions of the received signals to the BTradio IC circuitry 106B for further processing. FEM circuitry 104A mayalso include a transmit signal path which may include circuitryconfigured to amplify WLAN signals provided by the radio IC circuitry106A for wireless transmission by one or more of the antennas 101. Inaddition, FEM circuitry 104B may also include a transmit signal pathwhich may include circuitry configured to amplify BT signals provided bythe radio IC circuitry 106B for wireless transmission by the one or moreantennas. In the embodiment of FIG. 1, although FEM 104A and FEM 104Bare shown as being distinct from one another, embodiments are not solimited, and include within their scope the use of an FEM (not shown)that includes a transmit path and/or a receive path for both WLAN and BTsignals, or the use of one or more FEM circuitries where at least someof the FEM circuitries share transmit and/or receive signal paths forboth WLAN and BT signals.

Radio IC circuitry 106 as shown may include WLAN radio IC circuitry 106Aand BT radio IC circuitry 106B. The WLAN radio IC circuitry 106A mayinclude a receive signal path which may include circuitry todown-convert WLAN RF signals received from the FEM circuitry 104A andprovide baseband signals to WLAN baseband processing circuitry 108A. BTradio IC circuitry 106B may in turn include a receive signal path whichmay include circuitry to down-convert BT RF signals received from theFEM circuitry 104B and provide baseband signals to BT basebandprocessing circuitry 108B. WLAN radio IC circuitry 106A may also includea transmit signal path which may include circuitry to up-convert WLANbaseband signals provided by the WLAN baseband processing circuitry 108Aand provide WLAN RF output signals to the FEM circuitry 104A forsubsequent wireless transmission by the one or more antennas 101. BTradio IC circuitry 106B may also include a transmit signal path whichmay include circuitry to up-convert BT baseband signals provided by theBT baseband processing circuitry 108B and provide BT RF output signalsto the FEM circuitry 104B for subsequent wireless transmission by theone or more antennas 101. In the embodiment of FIG. 1, although radio ICcircuitries 106A and 106B are shown as being distinct from one another,embodiments are not so limited, and include within their scope the useof a radio IC circuitry (not shown) that includes a transmit signal pathand/or a receive signal path for both WLAN and BT signals, or the use ofone or more radio IC circuitries where at least some of the radio ICcircuitries share transmit and/or receive signal paths for both WLAN andBT signals.

Baseband processing circuitry 108 may include a WLAN baseband processingcircuitry 108A and a BT baseband processing circuitry 108B. The WLANbaseband processing circuitry 108A may include a memory, such as, forexample, a set of RAM arrays in a Fast Fourier Transform or Inverse FastFourier Transform block (not shown) of the WLAN baseband processingcircuitry 108A. Each of the WLAN baseband circuitry 108A and the BTbaseband circuitry 108B may further include one or more processors andcontrol logic to process the signals received from the correspondingWLAN or BT receive signal path of the radio IC circuitry 106, and toalso generate corresponding WLAN or BT baseband signals for the transmitsignal path of the radio IC circuitry 106. Each of the basebandprocessing circuitries 108A and 108B may further include physical layer(PHY) and medium access control layer (MAC) circuitry, and may furtherinterface with application processor 111 for generation and processingof the baseband signals and for controlling operations of the radio ICcircuitry 106.

Referring still to FIG. 1, according to the shown embodiment, WLAN-BTcoexistence circuitry 113 may include logic providing an interfacebetween the WLAN baseband circuitry 108A and the BT baseband circuitry108B to enable use cases requiring WLAN and BT coexistence. In addition,a switch 103 may be provided between the WLAN FEM circuitry 104A and theBT FEM circuitry 104B to allow switching between the WLAN and BT radiosaccording to application needs. In addition, although the antennas 101are depicted as being respectively connected to the WLAN FEM circuitry104A and the BT FEM circuitry 104B, embodiments include within theirscope the sharing of one or more antennas as between the WLAN and BTFEMs, or the provision of more than one antenna connected to each of FEM104A or 104B.

In some embodiments, the front-end module circuitry 104, the radio ICcircuitry 106, and baseband processing circuitry 108 may be provided ona single radio card, such as wireless radio card 102. In some otherembodiments, the one or more antennas 101, the FEM circuitry 104 and theradio IC circuitry 106 may be provided on a single radio card. In someother embodiments, the radio IC circuitry 106 and the basebandprocessing circuitry 108 may be provided on a single chip or integratedcircuit (IC), such as IC 112.

In some embodiments, the wireless radio card 102 may include a WLANradio card and may be configured for Wi-Fi communications, although thescope of the embodiments is not limited in this respect. In some ofthese embodiments, the radio architecture 100 may be configured toreceive and transmit orthogonal frequency division multiplexed (OFDM) ororthogonal frequency division multiple access (OFDMA) communicationsignals over a multicarrier communication channel. The OFDM or OFDMAsignals may comprise a plurality of orthogonal subcarriers.

In some of these multicarrier embodiments, radio architecture 100 may bepart of a Wi-Fi communication station (STA) such as a wireless accesspoint (AP), a base station or a mobile device including a Wi-Fi device.In some of these embodiments, radio architecture 100 may be configuredto transmit and receive signals in accordance with specificcommunication standards and/or protocols, such as any of the Instituteof Electrical and Electronics Engineers (IEEE) standards including, IEEE802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, IEEE 802.11bd, IEEE802.11p, IEEE 802.11ac, and/or IEEE 802.11ax standards and/or proposedspecifications for WLANs, although the scope of embodiments is notlimited in this respect. Radio architecture 100 may also be suitable totransmit and/or receive communications in accordance with othertechniques and standards.

In some embodiments, a road side unit (RSU), on board unit (OBU) and/orother device may perform one or more of the techniques, operationsand/or methods described herein.

In some embodiments, the radio architecture 100 may be configured forNext Generation Vehicle-to-Everything (NGV) communications, includingbut not limited to NGV communications in accordance with the IEEE802.11bd standard. In these embodiments, the radio architecture 100 maybe configured to communicate in accordance with an OFDM technique and/orOFDMA technique, although the scope of the embodiments is not limited inthis respect. In some embodiments, the radio architecture 100 may beconfigured for communications in accordance with the IEEE 802.11pstandard. In these embodiments, the radio architecture 100 may beconfigured to communicate in accordance with an OFDM technique and/orOFDMA technique, although the scope of the embodiments is not limited inthis respect.

In some other embodiments, the radio architecture 100 may be configuredto transmit and receive signals transmitted using one or more othermodulation techniques such as spread spectrum modulation (e.g., directsequence code division multiple access (DS-CDMA) and/or frequencyhopping code division multiple access (FH-CDMA)), time-divisionmultiplexing (TDM) modulation, and/or frequency-division multiplexing(FDM) modulation, although the scope of the embodiments is not limitedin this respect.

In some embodiments, as further shown in FIG. 1, the BT basebandcircuitry 108B may be compliant with a Bluetooth (BT) connectivitystandard such as Bluetooth, Bluetooth 4.0 or Bluetooth 5.0, or any otheriteration of the Bluetooth Standard. In embodiments that include BTfunctionality as shown for example in FIG. 1, the radio architecture 100may be configured to establish a BT synchronous connection oriented(SCO) link and/or a BT low energy (BT LE) link. In some of theembodiments that include functionality, the radio architecture 100 maybe configured to establish an extended SCO (eSCO) link for BTcommunications, although the scope of the embodiments is not limited inthis respect. In some of these embodiments that include a BTfunctionality, the radio architecture may be configured to engage in aBT Asynchronous Connection-Less (ACL) communications, although the scopeof the embodiments is not limited in this respect. In some embodiments,as shown in FIG. 1, the functions of a BT radio card and WLAN radio cardmay be combined on a single wireless radio card, such as single wirelessradio card 102, although embodiments are not so limited, and includewithin their scope discrete WLAN and BT radio cards

In some embodiments, the radio-architecture 100 may include other radiocards, such as a cellular radio card configured for cellular (e.g., 3GPPsuch as LTE, LTE-Advanced or 5G communications).

In some IEEE 802.11 embodiments, the radio architecture 100 may beconfigured for communication over various channel bandwidths includingbandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, 6GHz and bandwidths of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5 MHz, 8 MHz,10 MHz, 16 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or80+80 MHz (160 MHz) (with non-contiguous bandwidths). In someembodiments, the radio architecture 100 may be configured forcommunication in an ITS band at a center frequency at or near 5.9 GHz.In some embodiments, a 320 MHz channel bandwidth may be used. The scopeof the embodiments is not limited with respect to the above centerfrequencies however.

FIG. 2 illustrates FEM circuitry 200 in accordance with someembodiments. The FEM circuitry 200 is one example of circuitry that maybe suitable for use as the WLAN and/or BT FEM circuitry 104A/104B (FIG.1), although other circuitry configurations may also be suitable.

In some embodiments, the FEM circuitry 200 may include a TX/RX switch202 to switch between transmit mode and receive mode operation. The FEMcircuitry 200 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 200 may include alow-noise amplifier (LNA) 206 to amplify received RF signals 203 andprovide the amplified received RF signals 207 as an output (e.g., to theradio IC circuitry 106 (FIG. 1)). The transmit signal path of thecircuitry 200 may include a power amplifier (PA) to amplify input RFsignals 209 (e.g., provided by the radio IC circuitry 106), and one ormore filters 212, such as band-pass filters (BPFs), low-pass filters(LPFs) or other types of filters, to generate RF signals 215 forsubsequent transmission (e.g., by one or more of the antennas 101 (FIG.1)).

In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry200 may be configured to operate in either the 2.4 GHz frequencyspectrum or the 5 GHz frequency spectrum. In these embodiments, thereceive signal path of the FEM circuitry 200 may include a receivesignal path duplexer 204 to separate the signals from each spectrum aswell as provide a separate LNA 206 for each spectrum as shown. In theseembodiments, the transmit signal path of the FEM circuitry 200 may alsoinclude a power amplifier 210 and a filter 212, such as a BPF, a LPF oranother type of filter for each frequency spectrum and a transmit signalpath duplexer 214 to provide the signals of one of the differentspectrums onto a single transmit path for subsequent transmission by theone or more of the antennas 101 (FIG. 1). In some embodiments, BTcommunications may utilize the 2.4 GHZ signal paths and may utilize thesame FEM circuitry 200 as the one used for WLAN communications.

FIG. 3 illustrates radio IC circuitry 300 in accordance with someembodiments. The radio IC circuitry 300 is one example of circuitry thatmay be suitable for use as the WLAN or BT radio IC circuitry 106A/106B(FIG. 1), although other circuitry configurations may also be suitable.

In some embodiments, the radio IC circuitry 300 may include a receivesignal path and a transmit signal path. The receive signal path of theradio IC circuitry 300 may include at least mixer circuitry 302, suchas, for example, down-conversion mixer circuitry, amplifier circuitry306 and filter circuitry 308. The transmit signal path of the radio ICcircuitry 300 may include at least filter circuitry 312 and mixercircuitry 314, such as, for example, up-conversion mixer circuitry.Radio IC circuitry 300 may also include synthesizer circuitry 304 forsynthesizing a frequency 305 for use by the mixer circuitry 302 and themixer circuitry 314. The mixer circuitry 302 and/or 314 may each,according to some embodiments, be configured to provide directconversion functionality. The latter type of circuitry presents a muchsimpler architecture as compared with standard super-heterodyne mixercircuitries, and any flicker noise brought about by the same may bealleviated for example through the use of OFDM modulation. FIG. 3illustrates only a simplified version of a radio IC circuitry, and mayinclude, although not shown, embodiments where each of the depictedcircuitries may include more than one component. For instance, mixercircuitry 320 and/or 314 may each include one or more mixers, and filtercircuitries 308 and/or 312 may each include one or more filters, such asone or more BPFs and/or LPFs according to application needs. Forexample, when mixer circuitries are of the direct-conversion type, theymay each include two or more mixers.

In some embodiments, mixer circuitry 302 may be configured todown-convert RF signals 207 received from the FEM circuitry 104 (FIG. 1)based on the synthesized frequency 305 provided by synthesizer circuitry304. The amplifier circuitry 306 may be configured to amplify thedown-converted signals and the filter circuitry 308 may include a LPFconfigured to remove unwanted signals from the down-converted signals togenerate output baseband signals 307. Output baseband signals 307 may beprovided to the baseband processing circuitry 108 (FIG. 1) for furtherprocessing. In some embodiments, the output baseband signals 307 may bezero-frequency baseband signals, although this is not a requirement. Insome embodiments, mixer circuitry 302 may comprise passive mixers,although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 314 may be configured toup-convert input baseband signals 311 based on the synthesized frequency305 provided by the synthesizer circuitry 304 to generate RF outputsignals 209 for the FEM circuitry 104. The baseband signals 311 may beprovided by the baseband processing circuitry 108 and may be filtered byfilter circuitry 312. The filter circuitry 312 may include a LPF or aBPF, although the scope of the embodiments is not limited in thisrespect.

In some embodiments, the mixer circuitry 302 and the mixer circuitry 314may each include two or more mixers and may be arranged for quadraturedown-conversion and/or up-conversion respectively with the help ofsynthesizer 304. In some embodiments, the mixer circuitry 302 and themixer circuitry 314 may each include two or more mixers each configuredfor image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 302 and the mixer circuitry 314 may bearranged for direct down-conversion and/or direct up-conversion,respectively. In some embodiments, the mixer circuitry 302 and the mixercircuitry 314 may be configured for super-heterodyne operation, althoughthis is not a requirement.

Mixer circuitry 302 may comprise, according to one embodiment:quadrature passive mixers (e.g., for the in-phase (I) and quadraturephase (Q) paths). In such an embodiment, RF input signal 207 from FIG. 3may be down-converted to provide I and Q baseband output signals to besent to the baseband processor

Quadrature passive mixers may be driven by zero and ninety-degreetime-varying LO switching signals provided by a quadrature circuitrywhich may be configured to receive a LO frequency (f_(LO)) from a localoscillator or a synthesizer, such as LO frequency 305 of synthesizer 304(FIG. 3). In some embodiments, the LO frequency may be the carrierfrequency, while in other embodiments, the LO frequency may be afraction of the carrier frequency (e.g., one-half the carrier frequency,one-third the carrier frequency). In some embodiments, the zero andninety-degree time-varying switching signals may be generated by thesynthesizer, although the scope of the embodiments is not limited inthis respect.

In some embodiments, the LO signals may differ in duty cycle (thepercentage of one period in which the LO signal is high) and/or offset(the difference between start points of the period). In someembodiments, the LO signals may have a 25% duty cycle and a 50% offset.In some embodiments, each branch of the mixer circuitry (e.g., thein-phase (I) and quadrature phase (Q) path) may operate at a 25% dutycycle, which may result in a significant reduction is power consumption.

The RF input signal 207 (FIG. 2) may comprise a balanced signal,although the scope of the embodiments is not limited in this respect.The I and Q baseband output signals may be provided to low-noseamplifier, such as amplifier circuitry 306 (FIG. 3) or to filtercircuitry 308 (FIG. 3).

In some embodiments, the output baseband signals 307 and the inputbaseband signals 311 may be analog baseband signals, although the scopeof the embodiments is not limited in this respect. In some alternateembodiments, the output baseband signals 307 and the input basebandsignals 311 may be digital baseband signals. In these alternateembodiments, the radio IC circuitry may include analog-to-digitalconverter (ADC) and digital-to-analog converter (DAC) circuitry.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, or for otherspectrums not mentioned here, although the scope of the embodiments isnot limited in this respect.

In some embodiments, the synthesizer circuitry 304 may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 304 maybe a delta-sigma synthesizer, a frequency multiplier, or a synthesizercomprising a phase-locked loop with a frequency divider. According tosome embodiments, the synthesizer circuitry 304 may include digitalsynthesizer circuitry. An advantage of using a digital synthesizercircuitry is that, although it may still include some analog components,its footprint may be scaled down much more than the footprint of ananalog synthesizer circuitry. In some embodiments, frequency input intosynthesizer circuitry 304 may be provided by a voltage controlledoscillator (VCO), although that is not a requirement. A divider controlinput may further be provided by either the baseband processingcircuitry 108 (FIG. 1) or the application processor 111 (FIG. 1)depending on the desired output frequency 305. In some embodiments, adivider control input (e.g., N) may be determined from a look-up table(e.g., within a Wi-Fi card) based on a channel number and a channelcenter frequency as determined or indicated by the application processor111.

In some embodiments, synthesizer circuitry 304 may be configured togenerate a carrier frequency as the output frequency 305, while in otherembodiments, the output frequency 305 may be a fraction of the carrierfrequency (e.g., one-half the carrier frequency, one-third the carrierfrequency). In some embodiments, the output frequency 305 may be a LOfrequency (f_(LO)).

FIG. 4 illustrates a functional block diagram of baseband processingcircuitry 400 in accordance with some embodiments. The basebandprocessing circuitry 400 is one example of circuitry that may besuitable for use as the baseband processing circuitry 108 (FIG. 1),although other circuitry configurations may also be suitable. Thebaseband processing circuitry 400 may include a receive basebandprocessor (RX BBP) 402 for processing receive baseband signals 309provided by the radio IC circuitry 106 (FIG. 1) and a transmit basebandprocessor (TX BBP) 404 for generating transmit baseband signals 311 forthe radio IC circuitry 106. The baseband processing circuitry 400 mayalso include control logic 406 for coordinating the operations of thebaseband processing circuitry 400.

In some embodiments (e.g., when analog baseband signals are exchangedbetween the baseband processing circuitry 400 and the radio IC circuitry106), the baseband processing circuitry 400 may include ADC 410 toconvert analog baseband signals received from the radio IC circuitry 106to digital baseband signals for processing by the RX BBP 402. In theseembodiments, the baseband processing circuitry 400 may also include DAC412 to convert digital baseband signals from the TX BBP 404 to analogbaseband signals.

In some embodiments that communicate OFDM signals or OFDMA signals, suchas through baseband processor 108A, the transmit baseband processor 404may be configured to generate OFDM or OFDMA signals as appropriate fortransmission by performing an inverse fast Fourier transform (IFFT). Thereceive baseband processor 402 may be configured to process receivedOFDM signals or OFDMA signals by performing an FFT. In some embodiments,the receive baseband processor 402 may be configured to detect thepresence of an OFDM signal or OFDMA signal by performing anautocorrelation, to detect a preamble, such as a short preamble, and byperforming a cross-correlation, to detect a long preamble. The preamblesmay be part of a predetermined frame structure for Wi-Fi communication.

Referring back to FIG. 1, in some embodiments, the antennas 101 (FIG. 1)may each comprise one or more directional or omnidirectional antennas,including, for example, dipole antennas, monopole antennas, patchantennas, loop antennas, microstrip antennas or other types of antennassuitable for transmission of RF signals. In some multiple-inputmultiple-output (MIMO) embodiments, the antennas may be effectivelyseparated to take advantage of spatial diversity and the differentchannel characteristics that may result. Antennas 101 may each include aset of phased-array antennas, although embodiments are not so limited.

Although the radio-architecture 100 is illustrated as having severalseparate functional elements, one or more of the functional elements maybe combined and may be implemented by combinations ofsoftware-configured elements, such as processing elements includingdigital signal processors (DSPs), and/or other hardware elements. Forexample, some elements may comprise one or more microprocessors, DSPs,field-programmable gate arrays (FPGAs), application specific integratedcircuits (ASICs), radio-frequency integrated circuits (RFICs) andcombinations of various hardware and logic circuitry for performing atleast the functions described herein. In some embodiments, thefunctional elements may refer to one or more processes operating on oneor more processing elements.

FIG. 5 illustrates a WLAN 500 in accordance with some embodiments. TheWLAN 500 may include one or more APs 502, one or more Next GenerationVehicle-to-Everything (NGV) STAs 504, one or more legacy STAs 506 and/orother elements. In some embodiments, the WLAN 500 may not necessarilyinclude all of the elements shown in FIG. 5.

In some embodiments, the legacy devices 506 may support communication inaccordance with an IEEE 802.11p protocol, although the scope ofembodiments is not limited in this respect. In some embodiments, thelegacy devices 506 may operate in accordance with one or more IEEE802.11 protocols, such as IEEE 802.11 a/b/g/n/p/ac/ad/af/ah/aj/ay/ax, oranother legacy wireless communication standard. The legacy devices 506may be STAs or IEEE STAs. The NGV STAs 504 may be wireless transmit andreceive devices such as vehicles, OBUs, RSUs, portable devices(including devices that may be carried by pedestrians, bicycle ridersand/or other(s)), cellular telephone, portable electronic wirelesscommunication devices, smart telephone, handheld wireless device,wireless glasses, wireless watch, wireless personal device, tablet, oranother device that may be transmitting and receiving using the IEEE802.11 protocol such as IEEE 802.11p, IEEE 802.11bd or another wirelessprotocol. In some embodiments, an NGV STA 506 may support both 802.11p(legacy) and 802.11bd (NGV), although the scope of embodiments is notlimited in this respect.

The bandwidth of a channel may be 20 MHz, 40 MHz, or 80 MHz, 160 MHz,320 MHz contiguous bandwidths or an 80+80 MHz (160 MHz) non-contiguousbandwidth. In some embodiments, the bandwidth of a channel may be 1 MHz,1.25 MHz, 2.03 MHz, 2.5 MHz, 4.06 MHz, 5 MHz and 10 MHz, or acombination thereof or another bandwidth that is less or equal to theavailable bandwidth may also be used. In some embodiments the bandwidthof the channels may be based on a number of active data subcarriers. Insome embodiments the bandwidth of the channels is based on 26, 52, 106,242, 484, 996, or 2×996 active data subcarriers or tones that are spacedby 20 MHz. In some embodiments the bandwidth of the channels is 256tones spaced by 20 MHz. In some embodiments the channels are multiple of26 tones or a multiple of 20 MHz. In some embodiments a 20 MHz channelmay comprise 242 active data subcarriers or tones, which may determinethe size of a Fast Fourier Transform (FFT). An allocation of a bandwidthor a number of tones or sub-carriers may be termed a resource unit (RU)allocation in accordance with some embodiments. In some embodiments, abandwidth may be one of: 10, 20, 30, 40, 50, 60, and 70 MHz.

In some embodiments, the 26-subcarrier RU and 52-subcarrier RU are usedin 10 MHz, 20 MHz, 40 MHz, and 80 MHz OFDMA formats. In someembodiments, the 106-subcarrier RU is used in the 10 MHz, 20 MHz, 40MHz, and 80 MHz OFDMA formats. In some embodiments, the 242-subcarrierRU is used in 10 MHz, 20 MHz, 40 MHz, and 80 MHz OFDMA formats. In someembodiments, the 484-subcarrier RU is used in one or more of 10 MHz, 20MHz, 40 MHz, and 80 MHz OFDMA formats. In some embodiments, the996-subcarrier RU is used in one or more of 10 MHz, 20 MHz, 40 MHz, and80 MHz OFDMA formats. In some embodiments, including but not limited toembodiments in which down-clocking of elements in another 802.11protocol is used, sizes of the RUs in the other protocol may be dividedby 2. Embodiments are not limited to the numbers/values given above forbandwidth, number of subcarriers per RU, number of subcarriers, andother aspects. Other numbers/values may be used, in some embodiments.

Some embodiments relate to HE communications. In accordance with someIEEE 802.11 embodiments, e.g, IEEE 802.11ax embodiments, an AP 502 mayoperate as a master station which may be arranged to contend for awireless medium (e.g., during a contention period) to receive exclusivecontrol of the medium for an HE control period. In some embodiments, theHE control period may be termed a transmission opportunity (TXOP). TheAP 502 may transmit a HE master-sync transmission, which may be atrigger frame or HE control and schedule transmission, at the beginningof the HE control period. The AP 502 may transmit a time duration of theTXOP and sub-channel information. During the HE control period, STAs maycommunicate with the AP 502 in accordance with a non-contention basedmultiple access technique such as OFDMA or MU-MIMO. This is unlikeconventional WLAN communications in which devices communicate inaccordance with a contention-based communication technique, rather thana multiple access technique. During the HE control period, the AP 502may communicate with STAs using one or more HE frames. During the HEcontrol period, the STAs may operate on a sub-channel smaller than theoperating range of the AP 502. During the HE control period, legacystations refrain from communicating. The legacy stations may need toreceive the communication from the AP 502 to defer from communicating.

In accordance with some embodiments, during the TXOP the STAs maycontend for the wireless medium with the legacy devices 506 beingexcluded from contending for the wireless medium during the master-synctransmission. In some embodiments the trigger frame may indicate anuplink (UL) UL-MU-MIMO and/or UL OFDMA TXOP. In some embodiments, thetrigger frame may include a DL UL-MU-MIMO and/or DL OFDMA with aschedule indicated in a preamble portion of trigger frame.

In some embodiments, the multiple-access technique used during the HETXOP may be a scheduled OFDMA technique, although this is not arequirement. In some embodiments, the multiple access technique may be atime-division multiple access (TDMA) technique or a frequency divisionmultiple access (FDMA) technique. In some embodiments, the multipleaccess technique may be a space-division multiple access (SDMA)technique. In some embodiments, the multiple access technique may be aCode division multiple access (CDMA).

In example embodiments, the NGV STA, an apparatus of the NGV STA 504, adevice and/or an apparatus of the device may include one or more of thefollowing: the radio architecture of FIG. 1, the front-end modulecircuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or thebase-band processing circuitry of FIG. 4.

In example embodiments, the radio architecture of FIG. 1, the front-endmodule circuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or thebase-band processing circuitry of FIG. 4 may be configured to performthe methods and operations/functions herein described in conjunctionwith FIGS. 1-17.

In example embodiments, the NGV STA 504 and/or the AP 502 are configuredto perform the methods and operations/functions described herein inconjunction with FIGS. 1-17. The term Wi-Fi may refer to one or more ofthe IEEE 802.11 communication standards. In some embodiments, an NGV STAmay refer to an STA configured to operate as an NGV STA.

FIG. 6 illustrates a block diagram of an example machine 600 upon whichany one or more of the techniques (e.g., methodologies) discussed hereinmay perform. In alternative embodiments, the machine 600 may operate asa standalone device or may be connected (e.g., networked) to othermachines. In a networked deployment, the machine 600 may operate in thecapacity of a server machine, a client machine, or both in server-clientnetwork environments. In an example, the machine 600 may act as a peermachine in peer-to-peer (P2P) (or other distributed) networkenvironment. The machine 600 may be an AP 502, NGV STA 504, legacy STA506, personal computer (PC), a tablet PC, a set-top box (STB), apersonal digital assistant (PDA), a portable communications device, amobile telephone, a smart phone, a web appliance, a network router,switch or bridge, or any machine capable of executing instructions(sequential or otherwise) that specify actions to be taken by thatmachine. In some embodiments, devices that communicate in accordancewith 802.11p and/or 802.11bd may operate in accordance with an “Outsideof Context of BSS” (OCB) arrangement. In some embodiments, operation inaccordance with the OCB arrangement may include operation in which thedevices do not necessarily associate with an AP 502. Further, while onlya single machine is illustrated, the term “machine” shall also be takento include any collection of machines that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein, such as cloud computing,software as a service (SaaS), other computer cluster configurations.

Machine (e.g., computer system) 600 may include a hardware processor 602(e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 604 and a static memory 606, some or all of which may communicatewith each other via an interlink (e.g., bus) 608.

Specific examples of main memory 604 include Random Access Memory (RAM),and semiconductor memory devices, which may include, in someembodiments, storage locations in semiconductors such as registers.Specific examples of static memory 606 include non-volatile memory, suchas semiconductor memory devices (e.g., Electrically ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM)) and flash memory devices; magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; RAM; andCD-ROM and DVD-ROM disks.

The machine 600 may further include a display device 610, an inputdevice 612 (e.g., a keyboard), and a user interface (UI) navigationdevice 614 (e.g., a mouse). In an example, the display device 610, inputdevice 612 and UI navigation device 614 may be a touch screen display.The machine 600 may additionally include a mass storage (e.g., driveunit) 616, a signal generation device 618 (e.g., a speaker), a networkinterface device 620, and one or more sensors 621, such as a globalpositioning system (GPS) sensor, compass, accelerometer, or othersensor. The machine 600 may include an output controller 628, such as aserial (e.g., universal serial bus (USB), parallel, or other wired orwireless (e.g., infrared (IR), near field communication (NFC), etc.)connection to communicate or control one or more peripheral devices(e.g., a printer, card reader, etc.). In some embodiments the processor602 and/or instructions 624 may comprise processing circuitry and/ortransceiver circuitry.

The storage device 616 may include a machine readable medium 622 onwhich is stored one or more sets of data structures or instructions 624(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 624 may alsoreside, completely or at least partially, within the main memory 604,within static memory 606, or within the hardware processor 602 duringexecution thereof by the machine 600. In an example, one or anycombination of the hardware processor 602, the main memory 604, thestatic memory 606, or the storage device 616 may constitute machinereadable media.

Specific examples of machine readable media may include: non-volatilememory, such as semiconductor memory devices (e.g., EPROM or EEPROM) andflash memory devices; magnetic disks, such as internal hard disks andremovable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROMdisks.

While the machine readable medium 622 is illustrated as a single medium,the term “machine readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 624.

An apparatus of the machine 600 may be one or more of a hardwareprocessor 602 (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), a hardware processor core, or any combinationthereof), a main memory 604 and a static memory 606, sensors 621,network interface device 620, antennas 660, a display device 610, aninput device 612, a UI navigation device 614, a mass storage 616,instructions 624, a signal generation device 618, and an outputcontroller 628. The apparatus may be configured to perform one or moreof the methods and/or operations disclosed herein. The apparatus may beintended as a component of the machine 600 to perform one or more of themethods and/or operations disclosed herein, and/or to perform a portionof one or more of the methods and/or operations disclosed herein. Insome embodiments, the apparatus may include a pin or other means toreceive power. In some embodiments, the apparatus may include powerconditioning hardware.

The term “machine readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 600 and that cause the machine 600 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding or carrying data structures used by or associated withsuch instructions. Non-limiting machine readable medium examples mayinclude solid-state memories, and optical and magnetic media. Specificexamples of machine readable media may include: non-volatile memory,such as semiconductor memory devices (e.g., Electrically ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM)) and flash memory devices; magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; RandomAccess Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples,machine readable media may include non-transitory machine readablemedia. In some examples, machine readable media may include machinereadable media that is not a transitory propagating signal.

The instructions 624 may further be transmitted or received over acommunications network 626 using a transmission medium via the networkinterface device 620 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards, a LongTerm Evolution (LTE) family of standards, a Universal MobileTelecommunications System (UMTS) family of standards, peer-to-peer (P2P)networks, among others.

In an example, the network interface device 620 may include one or morephysical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or moreantennas to connect to the communications network 626. In an example,the network interface device 620 may include one or more antennas 660 towirelessly communicate using at least one of single-inputmultiple-output (SIMO), multiple-input multiple-output (MIMO), ormultiple-input single-output (MISO) techniques. In some examples, thenetwork interface device 620 may wirelessly communicate using MultipleUser MIMO techniques. The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine 600, and includesdigital or analog communications signals or other intangible medium tofacilitate communication of such software.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a machine readable medium. In an example, thesoftware, when executed by the underlying hardware of the module, causesthe hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

Some embodiments may be implemented fully or partially in softwareand/or firmware. This software and/or firmware may take the form ofinstructions contained in or on a non-transitory computer-readablestorage medium. Those instructions may then be read and executed by oneor more processors to enable performance of the operations describedherein. The instructions may be in any suitable form, such as but notlimited to source code, compiled code, interpreted code, executablecode, static code, dynamic code, and the like. Such a computer-readablemedium may include any tangible non-transitory medium for storinginformation in a form readable by one or more computers, such as but notlimited to read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory, etc.

FIG. 7 illustrates a block diagram of an example wireless device 700upon which any one or more of the techniques (e.g., methodologies oroperations) discussed herein may perform. The wireless device 700 may bean NGV device. The wireless device 700 may be an AP 502, NGV STA 504,legacy STA 506 (e.g., FIG. 5). An AP 502, NGV STA 504, legacy STA 506and/or other device may include some or all of the components shown inFIGS. 1-7. The wireless device 700 may be an example machine 600 asdisclosed in conjunction with FIG. 6.

The wireless device 700 may include processing circuitry 708. Theprocessing circuitry 708 may include a transceiver 702, physical layercircuitry (PHY circuitry) 704, and MAC layer circuitry (MAC circuitry)706, one or more of which may enable transmission and reception ofsignals to and from other wireless devices 700 (e.g., AP 502, NGV STA504, legacy STA 506 and/or other device) using one or more antennas 712.As an example, the PHY circuitry 704 may perform various encoding anddecoding functions that may include formation of baseband signals fortransmission and decoding of received signals. As another example, thetransceiver 702 may perform various transmission and reception functionssuch as conversion of signals between a baseband range and a RadioFrequency (RF) range.

Accordingly, the PHY circuitry 704 and the transceiver 702 may beseparate components or may be part of a combined component, e.g.,processing circuitry 708. In addition, some of the describedfunctionality related to transmission and reception of signals may beperformed by a combination that may include one, any or all of the PHYcircuitry 704 the transceiver 702, MAC circuitry 706, memory 710, andother components or layers. The MAC circuitry 706 may control access tothe wireless medium. The wireless device 700 may also include memory 710arranged to perform the operations described herein, e.g., some of theoperations described herein may be performed by instructions stored inthe memory 710.

The antennas 712 (some embodiments may include only one antenna) maycomprise one or more directional or omnidirectional antennas, including,for example, dipole antennas, monopole antennas, patch antennas, loopantennas, microstrip antennas or other types of antennas suitable fortransmission of RF signals. In some multiple-input multiple-output(MIMO) embodiments, the antennas 712 may be effectively separated totake advantage of spatial diversity and the different channelcharacteristics that may result.

One or more of the memory 710, the transceiver 702, the PHY circuitry704, the MAC circuitry 706, the antennas 712, and/or the processingcircuitry 708 may be coupled with one another. Moreover, although memory710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706,the antennas 712 are illustrated as separate components, one or more ofmemory 710, the transceiver 702, the PHY circuitry 704, the MACcircuitry 706, the antennas 712 may be integrated in an electronicpackage or chip.

In some embodiments, the wireless device 700 may be a mobile device asdescribed in conjunction with FIG. 6. In some embodiments the wirelessdevice 700 may be configured to operate in accordance with one or morewireless communication standards as described herein (e.g., as describedin conjunction with FIGS. 1-6, IEEE 802.11). In some embodiments, thewireless device 700 may include one or more of the components asdescribed in conjunction with FIG. 6 (e.g., display device 610, inputdevice 612, etc.) Although the wireless device 700 is illustrated ashaving several separate functional elements, one or more of thefunctional elements may be combined and may be implemented bycombinations of software-configured elements, such as processingelements including digital signal processors (DSPs), and/or otherhardware elements. For example, some elements may comprise one or moremicroprocessors, DSPs, field-programmable gate arrays (FPGAs),application specific integrated circuits (ASICs), radio-frequencyintegrated circuits (RFICs) and combinations of various hardware andlogic circuitry for performing at least the functions described herein.In some embodiments, the functional elements may refer to one or moreprocesses operating on one or more processing elements.

In some embodiments, an apparatus of or used by the wireless device 700may include various components of the wireless device 700 as shown inFIG. 7 and/or components from FIGS. 1-6. Accordingly, techniques andoperations described herein that refer to the wireless device 700 may beapplicable to an apparatus for a wireless device 700 (e.g., AP 502, NGVSTA 504, legacy STA 506 and/or other device), in some embodiments. Insome embodiments, the wireless device 700 is configured to decode and/orencode signals, packets, and/or frames as described herein, e.g., PPDUs.

In some embodiments, the MAC circuitry 706 may be arranged to contendfor a wireless medium during a contention period to receive control ofthe medium for a HE TXOP and encode or decode an HE PPDU. In someembodiments, the MAC circuitry 706 may be arranged to contend for thewireless medium based on channel contention settings, a transmittingpower level, and a clear channel assessment level (e.g., an energydetect level).

The PHY circuitry 704 may be arranged to transmit signals in accordancewith one or more communication standards described herein. For example,the PHY circuitry 704 may be configured to transmit a PPDU. The PHYcircuitry 704 may include circuitry for modulation/demodulation,upconversion/downconversion, filtering, amplification, etc. In someembodiments, the processing circuitry 708 may include one or moreprocessors. The processing circuitry 708 may be configured to performfunctions based on instructions being stored in a RAM or ROM, or basedon special purpose circuitry. The processing circuitry 708 may include aprocessor such as a general purpose processor or special purposeprocessor. The processing circuitry 708 may implement one or morefunctions associated with antennas 712, the transceiver 702, the PHYcircuitry 704, the MAC circuitry 706, and/or the memory 710. In someembodiments, the processing circuitry 708 may be configured to performone or more of the functions/operations and/or methods described herein.

In accordance with some embodiments, the Next GenerationVehicle-to-Everything (NGV) STA 504 may encode a physical layerconvergence procedure (PLCP) protocol data unit (PPDU) for transmissionin a dedicated short-range communication (DSRC) frequency band allocatedfor vehicular communication by NGV STAs 504 and legacy STAs 506. If thePPDU is to include traffic for an NGV service offered by the NGV STA504, the NGV STA 504 may encode the PPDU in accordance with an NGVenhanced physical (PHY) layer protocol. If the NGV STA 504 encodes thePPDU in accordance with the NGV enhanced PHY layer protocol, the PPDUmay be encoded to include a mid-amble, space-time block coding (STBC),or low-density parity check (LDPC) coding. If the PPDU is to include abasic safety message (BSM), the NGV STA 504 may encode the PPDU inaccordance with a legacy PHY layer protocol that is compatible with thelegacy STAs 506. If the NGV STA 504 encodes the PPDU in accordance withthe legacy PHY layer protocol: the mid-amble, the STBC, and the LDCPcoding may be excluded from the PPDU. These embodiments are described inmore detail below.

FIG. 8 illustrates the operation of a method of communication inaccordance with some embodiments. FIG. 9 illustrates the operation ofanother method of communication in accordance with some embodiments. Itis important to note that embodiments of the methods 800, 900 mayinclude additional or even fewer operations or processes in comparisonto what is illustrated in FIGS. 8-9. In addition, embodiments of themethods 800, 900 are not necessarily limited to the chronological orderthat is shown in FIGS. 8-9. In describing the methods 800, 900,reference may be made to one or more figures, although it is understoodthat the methods 800, 900 may be practiced with any other suitablesystems, interfaces and components.

In some embodiments, an NGV STA 504 may perform one or more operationsof the method 800, but embodiments are not limited to performance of themethod 800 and/or operations of it by the NGV STA 504. In someembodiments, another device and/or component may perform one or moreoperations of the method 800. In some embodiments, another device and/orcomponent may perform one or more operations that may be similar to oneor more operations of the method 800. In some embodiments, anotherdevice and/or component may perform one or more operations that may bereciprocal to one or more operations of the method 800. In anon-limiting example, the legacy STA 506 may perform an operation thatmay be the same as, similar to, reciprocal to and/or related to anoperation of the method 800, in some embodiments.

In some embodiments, an NGV STA 504 may perform one or more operationsof the method 900, but embodiments are not limited to performance of themethod 900 and/or operations of it by the NGV STA 504. In someembodiments, another device and/or component may perform one or moreoperations of the method 900. In some embodiments, another device and/orcomponent may perform one or more operations that may be similar to oneor more operations of the method 900. In some embodiments, anotherdevice and/or component may perform one or more operations that may bereciprocal to one or more operations of the method 900. In anon-limiting example, the legacy STA 506 may perform an operation thatmay be the same as, similar to, reciprocal to and/or related to anoperation of the method 900, in some embodiments.

It should be noted that one or more operations of one of the methods800, 900 may be the same as, similar to and/or reciprocal to one or moreoperations of the other method. For instance, an operation of the method800 may be the same as, similar to and/or reciprocal to an operation ofthe method 900, in some embodiments. In a non-limiting example, anoperation of the method 800 may include transmission of an element (suchas a frame, block, message and/or other) by an NGV STA 504, and anoperation of the method 900 may include reception of a same element(and/or similar element) by another NGV STA 504.

The method 800 may include operations related to transmission of PPDUs,signals and/or other elements, and the method 900 may include operationsrelated to reception of PPDUs, signals and/or other elements. In someembodiments, the NGV STA 504 may be configured to perform operationsfrom both methods 800, 900. For instance, the NGV STA 504 may beconfigured to transmit traffic for an NGV service, and may perform oneor more operations related to the method 800 to transmit the traffic.The NGV STA 504 may also be configured to receive traffic for an NGVservice from another NGV STA 504, and may perform one or more operationsrelated to the method 900 to receive the traffic.

In some cases, descriptions of operations and techniques described aspart of one of the methods 800, 900 may be relevant to the other method.Discussion of various techniques and concepts regarding one of themethods 800, 900 and/or other method may be applicable to one of theother methods, although the scope of embodiments is not limited in thisrespect.

The methods 800, 900 and other methods described herein may refer to APs502, NGV STAs 504, legacy STAs 506 and/or other devices configured tooperate in accordance with WLAN standards, 802.11 standards and/or otherstandards. However, embodiments are not limited to performance of thosemethods by those components, and may also be performed by other devices,such as an Evolved Node-B (eNB), User Equipment (UE) and/or other. Inaddition, the methods 800, 900 and other methods described herein may bepracticed by wireless devices configured to operate in other suitabletypes of wireless communication systems, including systems configured tooperate according to Third Generation Partnership Project (3GPP)standards, 3GPP Long Term Evolution (LTE) standards, 5G standards, NewRadio (NR) standards and/or other standards.

In some embodiments, the methods 800, 900 may also be applicable to anapparatus of an AP 502, an apparatus of an NGV STA 504, an apparatus ofa legacy STA 506 and/or an apparatus of another device. In someembodiments, an apparatus of an NGV STA 504 may perform one or moreoperations of the methods 800, 900 and/or other operations.

It should also be noted that embodiments are not limited by referencesherein (such as in descriptions of the methods 800, 900 and/or otherdescriptions herein) to transmission, reception and/or exchanging ofelements such as frames, messages, requests, indicators, signals orother elements. In some embodiments, such an element may be generated,encoded or otherwise processed by processing circuitry (such as by abaseband processor included in the processing circuitry) fortransmission. The transmission may be performed by a transceiver orother component, in some cases. In some embodiments, such an element maybe decoded, detected or otherwise processed by the processing circuitry(such as by the baseband processor). The element may be received by atransceiver or other component, in some cases. In some embodiments, theprocessing circuitry and the transceiver may be included in a sameapparatus. The scope of embodiments is not limited in this respect,however, as the transceiver may be separate from the apparatus thatcomprises the processing circuitry, in some embodiments.

One or more of the elements (such as messages, operations and/or other)described herein may be included in a standard and/or protocol,including but not limited to WLAN, IEEE 802.11, IEEE 802.11bd, 802.11p,IEEE 802.11ac, IEEE 802.11ax and/or other. The scope of embodiments isnot limited to usage of those elements, however. In some embodiments,different elements, similar elements, alternate elements and/or otherelements may be used. The scope of embodiments is also not limited tousage of elements that are included in standards.

In some embodiments, the NGV STA 504 may be arranged to operate inaccordance with an NGV protocol, including but not limited to 802.11bd.In some embodiments, the NGV STA 504 may be configured for unlicensedoperation, including but not limited to operation in a 6 GHz operatingfrequency band.

At operation 805, the NGV STA 504 may transmit a basic safety message(BSM). At operation 810, the NGV STA 504 may transmit signaling toannounce an NGV service. At operation 815, the NGV STA 504 may transmitsignaling to establish the NGV service. At operation 820, the NGV STA504 may transmit traffic for the NGV service. At operation 825, the NGVSTA 504 may encode one or more PPDUs. At operation 830, the NGV STA 504may transmit the one or more PPDUs.

It should be noted that there may be overlap between two or moreoperations shown in FIG. 8, in some embodiments. For instance, the NGVSTA 504 may encode a PPDU that includes a BSM, traffic for the NGVservice, information related to announcement of the NGV service, orinformation related to establishment of the NGV service.

In some embodiments, the NGV STA 504 may encode a physical layerconvergence procedure (PLCP) protocol data unit (PPDU) for transmissionin a dedicated short-range communication (DSRC) frequency band allocatedfor vehicular communication by NGV STAs and legacy STAs. If the PPDU isto include traffic for an NGV service offered by the NGV STA, the NGVSTA 504 may encode the PPDU in accordance with an NGV enhanced physical(PHY) layer protocol. In some embodiments, the NGV enhanced PHY may benon-compatible with the legacy STAs 504, although the scope ofembodiments is not limited in this respect. In some embodiments, the NGVenhanced PHY may be at least partly non-compatible with the legacy STAs504, although the scope of embodiments is not limited in this respect.

In some embodiments, if the NGV STA 504 encodes the PPDU in accordancewith the NGV enhanced PHY layer protocol, the PPDU may be encoded toinclude a mid-amble, space-time block coding (STBC), or low-densityparity check (LDPC) coding. If the PPDU is to include a basic safetymessage (BSM), the NGV STA 504 may encode the PPDU in accordance with alegacy PHY layer protocol that is compatible with the legacy STAs 506.If the NGV STA 504 encodes the PPDU in accordance with the legacy PHYlayer protocol: the mid-amble, the STBC, and the LDCP coding may beexcluded from the PPDU.

In some embodiments, the NGV STA 504 may encode the PPDU to include oneor more portions (such as the non-legacy portion of the preamble, dataportions, midambles) that are non-compatible with the legacy STAs 506.The NGV STA 504 may encode the PPDU to include the legacy portion of thepreamble, which may be compatible with the legacy STAs 506. Accordingly,one or more portions of the PPDU may be compatible with the legacy STAs506, and one or more other portions may be non-compatible with thelegacy STAs 506, in some embodiments.

In some embodiments, the NGV STA 504 may encode the PPDU in accordancewith the NGV enhanced PHY layer protocol or the legacy PHY layerprotocol to enable co-existence of NGV STAs 504 and legacy STAs 506 inthe DSRC frequency band.

In some embodiments, the NGV STA 504 may encode the PPDU in accordancewith the NGV enhanced PHY layer protocol if the PPDU includesinformation related to an establishment the NGV service. In someembodiments, the NGV STA 504 may encode the PPDU in accordance with thelegacy PHY layer protocol if the PPDU includes information related to anannouncement of the NGV service.

In some embodiments, the NGV STA 504 may encode the PPDU in accordancewith the legacy PHY layer protocol if the PPDU includes informationrelated to an announcement of a legacy service, an establishment of thelegacy service, or traffic for the legacy service.

In some embodiments, the NGV STA 504 and/or an apparatus of the NGV STA504 may be coupled to a plurality of transmit antennas. In someembodiments, the NGV STA 504 and/or an apparatus of the NGV STA 504 mayinclude the plurality of transmit antennas. In some embodiments, the NGVSTA 504 may encode the PPDU for cyclic shift diversity transmission onthe plurality of transmit antennas, wherein the NGV STA 504 may:generate a time signal based on the encoded PPDU; and for each transmitantenna of the plurality of transmit antennas, cyclically shift the timesignal by a corresponding cyclic shift delay (CSD) of a set of CSDs. Ifthe NGV STA 504 encodes the PPDU in accordance with the NGV enhanced PHYlayer protocol, the NGV STA 504 may cyclically shift the time signal byCSDs in a first set of CSDs. If the NGV STA 504 encodes the PPDU inaccordance with the legacy PHY layer protocol, the NGV STA 504 maycyclically shift the time signal by CSDs in a second set of CSDs. In anon-limiting example, the CSDs of the second set may be restricted tovalues that are less than or equal to 400 nanoseconds (nsec).Embodiments are not limited to usage of the number 400 nsec, however, asany suitable value may be used.

In some embodiments, if the NGV STA 504 encodes the PPDU in accordancewith the NGV enhanced PHY layer protocol, the NGV STA 504 may encode thePPDU to include: a first portion that includes a legacy portion of apreamble, wherein the legacy portion of the preamble includes a legacyshort training field (L-STF), a legacy long training field (L-LTF), anda legacy signal field (L-SIG); and a second portion that includes anon-legacy portion of the preamble and a data portion. The NGV STA 504may cyclically shift a first time signal for the first portion by CSDsof a first set of CSDs; and may cyclically shift a second time signalfor the second portion by CSDs of a second set of CSDs. In anon-limiting example, the CSDs of the first set may be restricted tovalues that are less than or equal to 400 nsec, and CSDs of the secondset may be restricted to values that are less than or equal to 1600nsec. Embodiments are not limited to these example numbers (400 and 1600nsec), however, as any suitable values may be used.

In some embodiments, if the NGV STA 504 encodes the PPDU in accordancewith the NGV enhanced PHY layer protocol, the NGV STA 504 may encode theL-SIG to include a length of the PPDU to spoof the legacy STAs 506 todefer transmissions to at least after transmission of the PPDU.

In some embodiments, the NGV STA 504 may encode the PPDU fortransmission in a 10 MHz channel of 64 sub-carriers spaced apart by156.25 kHz. In some embodiments, the NGV enhanced PHY layer protocoland/or the legacy PHY layer protocol may be based on down-clocking, by afactor of 2, of time signals for a 20 MHz channel of 64 sub-carriersspaced apart by 312.5 kHz.

In some embodiments, the NGV STA 504 may encode the PPDU fortransmission in a 20 MHz channel of 128 sub-carriers spaced apart by156.25 kHz. In some embodiments, the NGV enhanced PHY layer protocoland/or the legacy PHY layer protocol may be based on down-clocking, by afactor of 2, of time signals for a 40 MHz channel of 128 sub-carriersspaced apart by 312.5 kHz. Embodiments are not limited to thenumbers/values given above for sub-carriers, subcarrier spacings,bandwidths or other aspects. Other numbers/values may be used, in someembodiments.

In some embodiments, the DSRC frequency band may include one or morecontrol channels (CCHs) and one or more service channels (SCHs). The NGVSTA 504 may, if the PPDU includes traffic for the NGV service, encodethe PPDU for transmission on one of the SCHs. The NGV STA 504 may, ifthe PPDU includes a BSM, encode the PPDU for transmission on one of theCCHs. In some embodiments, the BSM may be transmitted on a dedicatedCCH, although the scope of embodiments is not limited in this respect.

In some embodiments, the vehicular communication for which the DSRCfrequency band is allocated may include one or more ofvehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V)communication, vehicle-to-infrastructure (V2I) communication,vehicle-to-pedestrian (V2P), and vehicle-to-network (V2N) communication.

In some embodiments, the NGV STA 504 may encode a PPDU for transmissionin a DSRC frequency band allocated for vehicular communication, whereinthe PPDU is encoded based on a co-existence of by NGV STAs 504 andlegacy STAs 506 in the DSRC frequency band. The NGV STA 504 may encodethe PPDU in accordance with an NGV enhanced PHY layer protocol or inaccordance with a legacy PHY layer protocol. The NGV enhanced PHY layerprotocol may include usage of one or more of: a mid-amble, space-timeblock coding (STBC), low-density parity check (LDPC) coding, and/orother aspect(s). The legacy PHY layer protocol may exclude usage of themid-amble, the STBC, and the LDCP coding.

In some embodiments, the NGV STA 504 may encode the PPDU in accordancewith the NGV enhanced PHY layer protocol if the PPDU includes trafficfor an NGV service. The NGV STA 504 may encode the PPDU in accordancewith the legacy PHY layer protocol if the PPDU includes a basic safetymessage (BSM).

In some embodiments, the NGV STA 504 may encode the PPDU fortransmission in a 10 MHz channel of 256 sub-carriers spaced apart by39.0625 kHz. In some embodiments, the NGV PHY layer protocol and/orlegacy PHY layer protocol may be based on down-clocking, by a factor of2, of time signals for a 20 MHz channel of 256 sub-carriers spaced apartby 78.125 kHz.

In some embodiments, an apparatus of an NGV STA 504 may comprise memory.The memory may be configurable to store at least a portion of a PPDU.The memory may store one or more other elements and the apparatus mayuse them for performance of one or more operations. The apparatus mayinclude processing circuitry, which may perform one or more operations(including but not limited to operation(s) of the method 800 and/orother methods described herein). The processing circuitry may include abaseband processor. The baseband circuitry and/or the processingcircuitry may perform one or more operations described herein, includingbut not limited to encoding of the PPDU. The apparatus may include atransceiver to transmit the PPDU. The transceiver may transmit and/orreceive other blocks, messages and/or other elements.

At operation 905, the NGV STA 504 may receive a BSM. At operation 910,the NGV STA 504 may receive signaling that announces an NGV service. Atoperation 915, the NGV STA 504 may receive signaling to establish theNGV service. At operation 920, the NGV STA 504 may determine a servicechannel (SCH) for reception of traffic for the NGV service. At operation925, the NGV STA 504 may receive traffic for the NGV service. Atoperation 930, the NGV STA 504 may receive one or more PPDUs. Atoperation 935, the NGV STA 504 may decode the one or more PPDUs.

In some embodiments, the NGV STA 504 may, in a control channel (CCH) ofa dedicated short-range communication (DSRC) frequency band allocatedfor vehicular communication, receive and/or decode a first PPDU thatannounces an NGV service offered by another NGV STA 504. The first PPDUmay be received and/or decoded in accordance with a legacy PHY layerprotocol. The NGV STA 504 may, in a service channel (SCH) of the DSRCfrequency band, receive and/or decode a second PPDU that includestraffic for the NGV service. The second PPDU may be received and/ordecoded in accordance with an NGV enhanced PHY layer protocol. In someembodiments, the NGV enhanced PHY layer protocol may include usage of amid-amble, space-time block coding (STBC), or low-density parity check(LDPC) coding. In some embodiments, the legacy PHY layer protocol mayexclude usage of a mid-amble, space-time block coding (STBC), orlow-density parity check (LDPC) coding.

In some embodiments, the NGV STA 504 may receive and/or decode anotherPPDU in accordance with the NGV enhanced PHY layer protocol. The otherPPDU may be received from the other NGV STA 504 and may include controlsignaling for an establishment of the NGV service. The NGV STA 504 maydetermine the SCH in which the traffic for the NGV service is to bereceived based on the control signaling.

FIG. 10 illustrates a dedicated short-range communication (DSRC)frequency allocation in accordance with some embodiments. FIG. 11illustrates a protocol stack in accordance with some embodiments. FIG.12 illustrates an example arrangement of multiple transmit chains inaccordance with some embodiments. FIG. 13 illustrates example elementsand fields in accordance with some embodiments.

It should be noted that the examples shown in FIGS. 10-13 may illustratesome or all of the concepts and techniques described herein in somecases, but embodiments are not limited by the examples. For instance,embodiments are not limited by the name, number, type, size, ordering,arrangement of elements (such as devices, operations, messages and/orother elements) shown in FIGS. 10-13. Although some of the elementsshown in the examples of FIGS. 10-13 may be included in a WLAN standard,Wi-Fi standard, 802.11 standard, 802.11bd standard, 802.11p standard,802.11ac standard, 802.11 ax standard and/or other standard, embodimentsare not limited to usage of such elements that are included instandards.

The DSRC band of 5.9 GHz (5.85-5.925 GHz) as depicted in FIG. 10 isreserved for vehicular communications, that is V2X (V2I/V2N/V2V/V2P)communications. The 802.11p standard is defined as the air interface andWAVE protocols (as shown in FIG. 11) have been specified on top of802.11p to enable different vehicular services. 802.11p PHY is simplythe 802.11a PHY (20 MHz, SISO) down-clocked by 2 in order to operate in10 MHz DSRC channels. 802.11p MAC defines transmission out of context ofBSS (OCB), which enables the vehicles to broadcast safety messageswithout association. The format of these safety messages and theircontent are defined in IEEE 1609 and SAE specifications, respectively.

Specifically in 1609, to ensure all cars receive high priority safetyrelated messages, there is a dedicated control channel (CCH) designatedfor this purpose. These messages follow the WAVE Short Message Protocol(WSMP). In SAE however, due to an FCC allocation of V2V safety messagesto Ch 172, the transmission of Basic Safety Messages (BSM) is mandatedto be on SCH 172. Hence in the US these messages are transmitted on SCH172, and in Europe these messages are transmitted on CCH (note that thechannelization in EU is different). In addition to WSMP messagestransmitted on CCH, 802.11p supporting devices can also announceservices on the CCH.

Devices that hear the service announcements of a service provider on theCCH, can then switch to the announced Service Channel (SCH) (accordingto TDMA rules specified for single-radio devices) to participate in dataexchange with the provider of the service. The transmissions on SCH canbe WSMP packets but also be IP based. The SCH transmissions can beeither unicast or broadcast. One possible use case could be thesee-through application. An example is where a car A can see though carB (in front A), by having the car B send in a P2P 802.11p or 802.11bdlink to car A, its data flow of its video showing what it sees in frontof it.

The packet transmissions on SCH channels can have some PHY parametersdefined per packet. For WSM packets the header carries Data rate,transmission power, and the SCH channel. For IP packets there is atransmission profile that includes this information.

In order to enhance the V2X services, IEEE 802.11 started a group (NextGeneration V2X, NGV) to develop the 802.11bd standard and to improve802.11p air interface to provide higher throughput (using e.g., MIMO,higher MCSs), better reliability (using e.g., LDPC) and longer range androbustness to high mobility (using e.g., extended range (DCM), STBC,mid-ambles), among other potential enhancements.

At the time 802.11bd comes to market, 802.11p may already be deployed,especially for safety services. New cars that implement the new 802.11bdtechnology to benefit from higher throughput, better range, and/or otheraspects may need to communicate with legacy STAs 506 already deployedusing 802.11p, and with new 802.11bd STAs using 802.11bd.

As a large proportion of the traffic is a simple broadcast of smallpackets by every STA 504, it may not be feasible to adapt the airinterface for such traffic on a per-receiving STA 504 basis. There maybe issues/challenges related to enabling the services with legacydevices 506 and to benefit from the better performance of 802.11bd.

Coexistence and backward compatibility are a requirement and a strengthfor 802.11p and 802.11bd, but it is also a complication as we want toensure there is no performance degradation introduced in expense ofbackward compatibility. For example, for specific services such assafety, we do not necessarily want to end up with having to send thebroadcast messages twice, one in a legacy 802.11p format in order to beunderstood by legacy cars and one in the new 802.11bd format to benefitfrom better PHY performance (such as range and/or other aspect(s)) asthis would increase the saturation of the safety channel.

In some embodiments, a new 802.11bd air interface may be defined,wherein the new air interface is understood by legacy 802.11p STAs(backward-compatible) but still provides improvements especially withregards to range: legacy compatible 11 ngv PPDU format (also referred toas NGV Control PHY herein). In some embodiments, another 802.11bd airinterface may also be defined, wherein the other air interface is notunderstood by legacy 802.11p STAs: legacy non-compatible 11ngv PPDUformat (also referred to as NGV Enhanced PHY herein).

In some embodiments, the NGV Control PHY PPDU is created through addingCSD (cyclic shift delays) to the 802.11a PPDU. It therefore allows tobenefit from spatial diversity at the transmitter side. We propose todefine CSD for up to 8 or even 16 antennas. Such approach would providea backward compatible way to increase the range, without thedisadvantages other possible approaches may introduce: CSD is usedinstead of STBC which is not backward compatible; mid-ambles will not bethat useful as the packets transmitted with 802.11bd control PHY airinterface will be short (broadcast packets for safety and for serviceannouncement); DCM and duplicated L-SIG are excluded from this design asthey are not backward compatible; LDPC also is not backward compatibleand hence not used; and/or other. It should be noted that this NGVControl PHY would either be specified in the 802.11 specification as anew PHY design as part of NGV PHY section, or could be an evolution ofthe 802.11p PHY specification. The NGV Enhanced PHY PPDU can includeadditional features for longer range, higher throughput andhigh-mobility support, including but not limited to: STBC, MIMO spatialmultiplexing, (beamforming), LDPC, higher QAM, mid-ambles and/orother(s). The design can be fully new or can simply reuse 802.1 lac(which already includes MIMO, STBC, LDPC, 256QAM) with a slightmodification to include mid-ambles.

To ensure the backward compatibility, the dual PHY design of NGV(Control PHY and Enhanced PHY) can be used in a number of differentways. For regulatory areas where the priority/basic safety messages arerequired to be transmitted on the CCH, the NGV Control PHY PPDU will beused on the CCH for broadcasting frames for safety use cases and serviceannouncements. The NGV enhanced PHY would then be used on SCHs. Hence,for the other services (where we have A) discovery of the services withthe broadcasted messages, B) establishment of the service, and C)exchange of data for the service in operation), the 11ngv control PHY isused for A, and the 11ngv enhanced PHY (legacy non-compatible PPDU) isused for B and C. The frame broadcasted in A) provides the PHY/MACcapability or capabilities of the device, so that the NGV Enhanced PHYPPDU can be used for B) and C) if the other device(s) also supports thisPPDU format. This information can be carried at the MAC level (A-ctlrfield for instance) or in higher layers (along with service discovery aspart of WSMP). WSM packets/Service announcement packets already providesome PHY parameters to be used for the SCH, and this may be extended toinclude new information.

Some or all PHY features for the NGV Enhanced PHY PPDU should bemandatory, so that the capability indication could potentially be assmall as 1 bit. If there are optional features specified, the providermay announce the capability, however, they cannot be used for broadcastservices. For unicast/p2p services, there may be MAC exchanges tonegotiate the optional features. Some or all MAC features for the NGVEnhanced PHYPPDU should be mandatory, so that the capability indicationcan be as small as 1 bit. The support for block-Ack should be mandatoryand be enabled without negotiation and with a single set of possibleparameters. If there are optional features specified, the provider mayannounce the capability, however, they cannot be used for broadcastservices. For unicast/p2p services, there may be MAC exchanges tonegotiate the optional features.

Operation B) and C) can be done with the NGV Enhanced PHY PPDU on theSCH. It can also be done potentially utilizing the 802.11ac or 802.1 laxair interface in the 2.4 or 5 GHz bands. We therefore propose to modifythe current 1609.4 (WAVE multi-channel operation) protocol to enable theuse of regular Wi-Fi radio for B) and C) in other bands than the ITSband.

In some embodiments, for regulatory regions that the priority/safetymessages are required to be transmitted on a SCH (like channel 172 inthe US), 11NGV control PHY will be used on that particular SCH and alsoon CCH for broadcasting services on other channels.

In some embodiments, backward compatibility may be realized by mandatinguse of the NGV Control PHY for all the services that already exist. Someservices already defined may use relatively short packets (such asaverage 300 bytes) and existing 802.11p PHY has been proven to besufficient for them. As new services are defined, they may require thenew 11NGV enhanced PHY. The service announcements for the new serviceson CCH can be using either 11NGV control PHY or 11NGV enhanced PHY.

It should be noted that the dual PHY design proposed here is independentof single or multi-radio operation of DSRC and there is no changesrequired in that respect compared to the operations today.

In some embodiments, a design for the NGV Control PHYair interface mayinclude adding CSDs to the 802.11a PPDU.

In FIG. 12, an example 1200 illustrates a transmit block diagram forL-SIG and data adding CSD in the red portion.

The table below (referred to as Table 1 herein) illustrates cyclic shiftvalues for preamble, using figures from 802.11ac.

T_(CS) ^(i) ^(TX) values for L-STF, L-LTF, L-SIG fields of the PPDUTotal number of transmit chain (N_(TX)) per Cyclic shift for transmitchain i_(TX) (in units of ns) frequency segment 1 2 3 4 5 6 7 8 >8 1 0 —— — — — — — — 2 0 −200 — — — — — — — 3 0 −100 −200 — — — — — — 4 0 −50−100 −150 — — — — — 5 0 −175 −25 −50 −75 — — — — 6 0 −200 −25 −150 −175−125 — — — 7 0 −200 −150 −25 −175 −75 −50 — — 8 0 −175 −150 −125 −25−100 −50 −200 — >8 0 −175 −150 −125 −25 −100 −50 −200 Between −200 and 0inclusive

The table below (referred to as Table 2 herein) illustrates cyclic shiftvalues for modulated part, using figures from 802.11ac.

T_(CS, VHT)(n) values for the VHT modulated fields of a PPDU Totalnumber of space-time streams Cyclic shift for space-time stream n (ns)(N_(STS, total)) 1 2 3 4 5 6 7 8 1 0 — — — — — — — 2 0 −400 — — — — — —3 0 −400 −200 — — — — — 4 0 −400 −200 −600 — — — — 5 0 −400 −200 −600−350 — — — 6 0 −400 −200 −600 −350 −650 — — 7 0 −400 −200 −600 −350 −650−100 — 8 0 −400 −200 −600 −350 −650 −100 −750

These values should be redefined from 802.11n/ac/ax to meet the needs ofthis system. First it should be increased to exploit the larger GI thatis utilized in this system. Additionally, the CSDs may be redefined withthe following constraints: making sure the maximum delay does notdegrade performance in outdoor channels (or large area indoor channels)such that the total delay (Tx/Rx filtering/CSD and channel) does notexceed the GI length introducing inter carrier interference; largeenough to be effective (convert well into frequency diversity gains) inoutdoor environments, and exploiting the fact that the guard interval is1.6 us instead of 0.8 us for 802.11ac when those figures were computed.

In some embodiments, in 802.11n/ac/ax, the CSD values applied to thelegacy portion of the preamble (L-STF, L-LTF and L-SIG) were set(compromise) to be limited to 200 ns, as shown in Table 1.

As 802.11p is a down clocked version of 802.11a, the CSD values that canbe applied on the STF, LTF, SIG and DATA for the NGV Control PHY can bedoubled compared to 802.11a. The new values would then be exactlyidentical to values in Table 1, but multiplied by 2, to be equal orlower than 400 ns. The result is illustrated in Table 3 below.

T_(CS) ^(i) ^(TX) values for L-STF, L-LTF, L-SIG, Data fields of the NGVControl PHY PPDU Total number of transmit chains (N_(TX)) per Cyclicshift for transmit chain i_(TX) (in units of ns) frequency segment 1 2 34 5 6 7 8 >8 1 0 — — — — — — — — 2 0 −400 — — — — — — — 3 0 −200 −400 —— — — — — 4 0 −100 −200 −300 — — — — — 5 0 −350 −50 −100 −150 — — — — 60 −400 −50 −300 −350 −250 — — — 7 0 −400 −300 −50 −350 −150 −100 — — 8 0−350 −300 −250 −50 −200 −100 −400 — >8 0 −350 −300 −250 −50 −200 −10−400 Between −400 and 0 inclusive

In some embodiments, the cyclic shifs that are applied to the NGVControl PHY may be increased, so that they are higher than 400 ns.

In some embodiments, a new 802.11bd air interface may be defined,wherein the new 802.11bd air interface is understood by legacy 11p STAs(forward-compatible) but still provides improvements especially withregards to range: legacy compatible 11ngv PPDU format (also referred toas NGV Control PHY herein). In addition, another 802.11bd air interfacemay be defined, wherein the other 802.11nv air interface is notunderstood by legacy 11p STAs: legacy non-compatible 11ngv PPDU format(also referred to as NGV Enhanced PHY herein). The NGV Control PHY PPDUis created through adding CSD (cyclic shift delays) to the 802.11a PPDU.It therefore allows to benefit from spatial diversity at the transmitterside. We propose to define CSD for up to 8 or even 16 antennas. The NGVEnhanced PHY PPDU can include one or more new features for longer range,higher throughput and high-mobility support. One or more of STBC, MIMOspatial multiplexing, (beamforming), LDPC, higher QAM, mid-ambles and/orother may be used.

In some embodiments, cyclic shifts (CSDs) may be applied to the NGVEnhanced PHY.

In some embodiments, a mixed-mode approach may be used, which will bedescribed below. In some embodiments, a Greenfield mode approach may beused, which will also be described below.

In the mixed-mode approach, the NGV Enhanced PHY PPDU may include 2parts. A first part is the 11p legacy preamble containing the L-STF, theL-LTF and the L-SIG fields, and a second part is a non-legacy portion ofthe preamble, the data portion and the Packet Extension (if present).

In some embodiments, the NGV Enhanced PHY PPDU can be a downclocked-by-2version of the 11ac VHT PPDU. In such case, the part 1 would alsoinclude the newly defined NGV_SIG_A, as shown in 1300 in FIG. 13(replacing VHT terms with NGV term).

In some embodiments, the NGV Enhanced PHY PPDU can be a downclocked-by-2version of the 802.11ax HE PPDU. In such case, the part 1 would alsoinclude the newly defined NGV_SIG_A, as shown in 1300 in FIG. 13(replacing VHT terms with NGV term). In some embodiments, the NGVEnhanced PHY PPDU can be a downclocked-by-2 version of the 802.11n HTPPDU. In some cases, the part 1 would also include the newly definedNGV_SIG_A, as shown in 1300 in FIG. 13 (replacing HT terms with NGVterm). In some embodiments, even if the design is new, the second partmay start with the NGV-STF field, and may include NGV-LTFs. In someembodiments, different sets of cyclic shift values may be applied forpart 1 and for part 2, with part 1 CSD values being lower than part 2CSD values. In some embodiments, these CSD values for part 1 may be setas the CSD values used for the legacy part of 802.11n, 802.11ac and/or802.1 lax, multiplied by 2 as the signal is down-clocked by 2. That maymean that they are lower than or equal to 400 ns, although the scope ofembodiments is not limited in this respect. This may provide moreflexibility in assigning CSD's to different antenna and provides moreseparation in time for the antenna transmissions then possible withlegacy versions of Wi-Fi.

In some embodiments, the CSD values for part 2 may be set as the CSDvalues used for the non-legacy part of 802.11ac and/or 802.11ax,multiplied by 2 as the signal is down-clocked by 2. That may mean thatthey are lower than or equal to 1600 ns, although the scope ofembodiments is not limited in this respect. Again, for this region, thelarger time may provide more flexibility and separation in time betweenthe antennas.

In FIG. 13, an NGV Enhanced PPDU format 1300 is illustrated with the 2parts identified if the design follows the 802.11ac VHT design (notethat one or more of the names of the fields may be changed, in someembodiments).

In FIG. 13, an NGV Enhanced PPDU format 1350 is illustrated with the 2parts identified If the design follows the 802.11ax HE design (note thatone or more of the HE names of the fields may be changed to NGV, in someembodiments).

In some embodiments, a greenfield mode design may be used. In someembodiments, the design may be used on channels in which only NGVservices are allowed, although the scope of embodiments is not limitedin this respect. In some embodiments, the PPDU only has a single part asit does not include L-STF, L-LTF and L-SIG. In some embodiments, the CSDvalues could in this case be the same for the entire PPDU, and could beincreased as in part 2 of the mixed mode format.

In some cases, one or more of the techniques, operations and/or methodsdescribed herein may enable usage of lower CSD values for the part thatis decoded by legacy 11p devices, whose detection performance would beimpacted by larger CSD values. Basically the periodicity of the STF issuch that large delays, larger than the period of the STS sequencerepetitions, can degrade detection performance and accuracy (largely intime) of the preamble. In some cases, one or more of the techniques,operations and/or methods described herein may enable the system to havelarger CSD values for the data portion of the NGV Enhanced PHY PPDU, inorder to provide more time separation of the antennas and improve MIMOperformance. This may be especially true for cases in which higher orderMIMO modes are utilized, although the scope of embodiments is notlimited in this respect.

The tables below (referred to as Table 4 and Table 5), illustrate valuesof CSD if values defined in 802.11n/ac/ax are multiplied by 2. Table 4below illustrates proposed cyclic shift values for part 1 of the NGVEnhanced PHY PPDU.

T_(CS) ^(i) ^(TX) values for L-STF, L-LTF, L-SIG, NGV-SIG fields of theNGV Enhanced PHY PPDU Total number of transmit chains (N_(TX)) perCyclic shift for transmit chain i_(TX) (in units of ns) frequencysegment 1 2 3 4 5 6 7 8 >8 1 0 — — — — — — — — 2 0 −400 — — — — — — — 30 −200 −400 — — — — — — 4 0 −100 −200 −300 — — — — — 5 0 −350 −50 −100−150 — — — — 6 0 −400 −50 −300 −350 −250 — — — 7 0 −400 −300 −50 −350−150 −100 — — 8 0 −350 −300 −250 −50 −200 −100 −400 — >8 0 −350 −300−250 −50 −200 −10 −400 Between −400 and 0 inclusive

Table 5 below illustrates proposed cyclic shift values for part 2 of NGVEnhanced PHY PPDU.

T_(CS, VHT)(n) value for the NGV modulated fields of a PPDU Total numberof space-time streams Cyclic shift for space-time stream n (ns)(N_(STS, total)) 1 2 3 4 5 6 7 8 1 0 — — — — — — — 2 0 −800 — — — — — —3 0 −800 −400 — — — — — 4 0 −800 −400 −1200 — — — — 5 0 −800 −400 −1200−700 — — — 6 0 −800 −400 −1200 −700 −1300 — — 7 0 −800 −400 −1200 −700−1300 −200 — 8 0 −800 −400 −1200 −700 −1300 −200 −1500

In some embodiments, values of the cyclic shifts that are applied to theNGV Enhanced PHY may be higher than 400 ns in part 1 and higher than1600 ms in part 2.

The Abstract is provided to comply with 37 C.F.R. Section1.72(b)requiring an abstract that will allow the reader to ascertain the natureand gist of the technical disclosure. Itis submitted with theunderstanding that it will not be used to limit or interpret the scopeor meaning of the claims. The following claims are hereby incorporatedinto the detailed description, with each claim standing on its own as aseparate embodiment.

1. (canceled)
 2. An apparatus for a next generationvehicle-to-everything (NGV) station (STA), the apparatus comprising:processing circuitry; and memory, wherein the processing circuitry isconfigured to: encode an NGV physical layer convergence procedure (PLCP)protocol data unit (PPDU) in accordance with an NGV physical (PHY) layerprotocol for transmission of data outside the context of a basic serviceset (OCB), the NGV PPDU to include a midamble, and wherein a NGV PHYdata payload of the NGV PPDU is encoded by low-density parity check(LDPC) coding.
 3. The apparatus of claim 2, wherein the midamble ispresent in the NGV PHY data payload of the NGV PPDU.
 4. The apparatus ofclaim 3, wherein the processing circuitry is configured to encode anon-NGV PPDU for transmission of data when not OCB, the non-NGV PPDU toexclude the midamble.
 5. The apparatus of claim 4, wherein a datapayload of the non-NGV PPDU is encoded by one of space-time block coding(STBC) and the LDCP coding.
 6. The apparatus of claim 5, wherein for a10 MHz channel transmission, the NGV PPDU is encoded for a 10 MHz NGVPPDU transmission in a 10 MHz channel divided into 64 subcarriers. 7.The apparatus of claim 6, wherein for a 20 MHz channel transmission, theNGV PPDU is encoded for a 20 MHz NGV PPDU transmission in a 20 MHzchannel divided into 128 subcarriers.
 8. The apparatus of claim 7,wherein the processing circuitry is further configured to refrain fromencoding the NGV PHY data payload of the NGV PPDU using STBC.
 9. Theapparatus of claim 3, wherein the NGV STA is configured for use in avehicular environment and is configured to transmit and receivebroadcast and unicast data frames OCB.
 10. The apparatus of claim 9wherein the memory is configured to store the NGV PHY data payload. 11.A non-transitory computer-readable storage medium that storesinstructions for execution by processing circuitry of a next generationvehicle-to-everything (NGV) station (STA), wherein the processingcircuitry is configured to: encode an NGV physical layer convergenceprocedure (PLCP) protocol data unit (PPDU) in accordance with an NGVphysical (PHY) layer protocol for transmission of data outside thecontext of a basic service set (OCB), the NGV PPDU to include amidamble, and wherein a NGV PHY data payload of the NGV PPDU is encodedby low-density parity check (LDPC) coding.
 12. The non-transitorycomputer-readable storage medium of claim 11, wherein the midamble ispresent in the NGV PHY data payload of the NGV PPDU.
 13. Thenon-transitory computer-readable storage medium of claim 12, wherein fora 10 MHz channel transmission, the NGV PPDU is encoded for a 10 MHz NGVPPDU transmission in a 10 MHz channel divided into 64 subcarriers. 14.The non-transitory computer-readable storage medium of claim 13, whereinfor a 20 MHz channel transmission, the NGV PPDU is encoded for a 20 MHzNGV PPDU transmission in a 20 MHz channel divided into 128 subcarriers.15. The non-transitory computer-readable storage medium of claim 14,wherein the processing circuitry is further configured to refrain fromencoding the NGV PHY data payload of the NGV PPDU using STBC.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein theprocessing circuitry is configured to encode a non-NGV PPDU fortransmission of data when not OCB, the non-NGV PPDU to exclude themidamble.
 17. The non-transitory computer-readable storage medium ofclaim 16, wherein a data payload of the non-NGV PPDU is encoded by oneof space-time block coding (STBC) and the LDCP coding.
 18. An apparatusfor access point (AP), the apparatus comprising: processing circuitry;and memory, wherein the processing circuitry is configured to: decode anext generation vehicle-to-everything (NGV) physical layer convergenceprocedure (PLCP) protocol data unit (PPDU) in accordance with an NGVphysical (PHY) layer protocol for reception of data outside the contextof a basic service set (OCB), the NGV PPDU to include a midamble; anddecode a non-NGV PPDU for reception of data when not OCB, the non-NGVPPDU to exclude the midamble.
 19. The apparatus of claim 18, wherein aNGV PHY data payload of the NGV PPDU is encoded by low-density paritycheck (LDPC) coding, and wherein a data payload of the non-NGV PPDU isencoded by one of space-time block coding (STBC) and the LDCP coding.20. The apparatus of claim 19, wherein the midamble is present in theNGV PHY data payload of the NGV PPDU.
 21. The apparatus of claim 20,wherein for a 10 MHz channel transmission, the NGV PPDU is encoded for a10 MHz NGV PPDU transmission in a 10 MHz channel divided into 64subcarriers, and wherein for a 20 MHz channel transmission, the NGV PPDUis encoded for a 20 MHz NGV PPDU transmission in a 20 MHz channeldivided into 128 subcarriers.